feat!: integrate Uhura 0.4 into Spock - #26

Ready status

gridaco/uhura#24 merged first as 896aa6b. This branch now records that exact Uhura main revision in bf2ec17, and both the ordinary PR suite and the non-publishing package workflow have passed on the synchronized head.

Summary

• advance the embedded Uhura checkout to the reviewed 0.4 machine-first language and runtime;
• align Spock host, packaged sidecar, Editor, Play, inspection, IR, view, and adapter-provider protocol contracts;
• admit the current uhura-editor-state/5, uhura-machine-inspection/1, and uhura-inspection/1 read models;
• add an explicit checked-route admission boundary so application routes cannot collide with Spock-owned namespaces;
• preserve Editor publication while retaining the last good Play generation when a route collision is introduced;
• replace the legacy page/catalog/fixture starter with the canonical machine.uhura, ui.uhura, evidence.uhura, host.toml, and uhura.toml project shape;
• remove stale 0.3 fixture paths and align framework diagnostics with strict 0.4 identities;
• update package workflow assertions, sidecar verification, public docs, installable Uhura skill, and website framing.

Why

Uhura 0.4 replaces the previous page-first language with a machine-first language and new host/runtime contracts. Spock is the framework consumer of that language, so its embedded revision, packaged assets, generated starter, tests, skills, and public documentation must move together or a newly scaffolded project cannot be checked and served coherently.

Impact

This is intentionally breaking for the unreleased source-level Uhura integration. spock new now creates a complete Uhura 0.4 counter application with an explicit machine, UI projection, evidence, and host binding. Existing Spock authority behavior is unchanged.

The checked route view is now consumed through one host admission boundary. Spock-owned namespaces remain protected while similarly prefixed application routes remain valid.

Validation

• cargo fmt --all -- --check;
• cargo clippy --offline --locked --workspace --all-targets -- -D warnings;
• cargo test --offline --locked --workspace --all-targets;
• cargo run --offline --locked -p spock-cli -- check uhura/examples/instagram — 91 previews, 34 replay-derived previews, one expected unchecked provider warning;
• SPOCK_BIN=target/debug/spock node scripts/check-doc-snippets.mjs — 34 snippets checked, 0 skipped;
• corepack pnpm@10.11.0 -C www build — 35 pages, zero diagnostics;
• public spock-lang and uhura-lang skills pass the canonical validator;
• host route-admission, aggregate Editor/Play, packaged-sidecar, and protocol-focused suites passed;
• live combined-host Editor/Play smoke passed with no browser warnings or errors;
• non-publishing npm.yml run 29815243964 passed on bf2ec17: four native builds, Linux/macOS/Windows installed-package verification, and an exact 21-file package of 26,501,976 bytes under the documented 26 MiB cap. The real publish step was skipped.

Final checkpoints

• a16797c — integrate the reviewed Uhura 0.4 revision and align Spock's host, templates, protocols, skills, tests, and documentation;
• b4b8590 — close the final route-admission and aggregate Editor/Play review gaps;
• 8818c97 — admit the measured Uhura 0.4 npm package under an explicit 26 MiB guard;
• 3d29f67 — make the package dry-run path reusable after a version already exists, without enabling a real publish;
• bf2ec17 — synchronize the gitlink to the merged Uhura 0.4 main revision.

Completed dependency order

1. feat!: replace Uhura with the 0.4 machine-first language uhura#24 merged as 896aa6b.
2. This PR synchronized its uhura gitlink in bf2ec17.
3. Spock CI and the non-publishing npm package workflow passed on that exact head.

Companion PR

• Uhura 0.4 language and runtime replacement: feat!: replace Uhura with the 0.4 machine-first language uhura#24